(v1) Tour Guide App
Layout
Criteria | Meet Specification |
---|---|
Overall Layout |
App contains at least 4 lists of relevant attractions for a location |
Navigation |
User can navigate between lists using a central screen, a NavDrawer, or a View pager. |
List Item Contents |
Each list item contains information about an event, restaurant, historical site, or similar. |
Pictures |
At least one list includes pictures of the location. |
Layout Best Practices |
The code adheres to all of the following best practices:
|
Functionality
Criteria | Meet Specification |
---|---|
Location Object |
App contains a custom object for storing location information . |
Custom Adapter |
App uses a custom adapter to populate the layout with views based on instances of the custom class. |
String Storage |
All strings are stored in the strings.xml resource file. |
Image Storage |
All images are stored as drawables. All drawables are stored at multiple densities. |
Errors |
The code runs without errors. |
Code Readability
Criteria | Meet Specification |
---|---|
Readability |
Code is easily readable such that a fellow programmer can understand the purpose of the app. |
Naming Conventions |
All variables, methods, and resource IDs are descriptively named such that another developer reading the code can easily understand their function. |
Formatting |
The code is properly formatted:
The code also has proper indentation when defining variables and methods. |